@meaton, thank you very much for your reply. As a followup, is there a way for NETransparentProxyProvider Two to identify the process which the flow is originated from? Should we raise a Feedback in order to achive this?

Identifing the process which the flow is originated from in NETransparentProxyProvider One shouldn't be a problem. It's the scenario where NETransparentProxyProvider Two is only seeing network traffic generated from NETransparentProxyProvider One. Is there a way for NETransparentProxyProvider Two to know the true source of the flow? As far as we can tell now, NETransparentProxyProvider Two will identify all incoming flow to have been generated from the process of NETransparentProxyProvider One.

Our currently sitituation is that when our product is NETransparentProxyProvider Two and another vendor is NETransparentProxyProvider One, we are unable to identify the originating process of the flow content. We curerntly use the flow.metadata to identify the originating process as a browser. However, we do not have that ability being NETransparentProxyProvider Two as flow.metadata reflects process information of NETransparentProxyProvider One. Is there anyway of being NETransparentProxyProvider Two and knowing the originating process information that was intercepted by NETransparentProxyProvider One?

What does the OSStatus error -10811. mean in this context?